{"id":18811,"date":"2023-02-17T13:56:30","date_gmt":"2023-02-17T18:56:30","guid":{"rendered":"https:\/\/carleton.ca\/webservices\/?p=18811"},"modified":"2024-06-08T22:04:42","modified_gmt":"2024-06-09T02:04:42","slug":"scantastic-news-for-accessible-websites","status":"publish","type":"post","link":"https:\/\/carleton.ca\/webservices\/2023\/scantastic-news-for-accessible-websites\/","title":{"rendered":"Scantastic news for accessible websites"},"content":{"rendered":"\n
\n
\n\n
\n
\n
\n

\n Scantastic news for accessible websites\n <\/h1>\n \n \n <\/header>\n\n <\/div>\n\n <\/div>\n\n <\/div>\n<\/section>\n\n

As we have said before, the community of people who maintain websites at Carleton (that\u2019s you!) is great at being supportive and proactive about accessibility. To maintain this momentum, we are offering to scan websites for accessibility, to check for any errors in our template or your content.<\/p>\n\n\n\n

How we assess accessibility<\/h2>\n\n\n\n

There are two elements to the process. To start, we use a third-party application called PopeTech to scan a website. This involves counting the number of pages, posts, events, and any other types of post or page on the site and feeding the total into the application. It indexes every page and post on the site. We can then run the scan over all those indexed pages.<\/p>\n\n\n\n

The other part of the process is browsing through the site to sample a portion of the content. (We look at between ten and twenty percent of all pages.) This is because not every component of web content can be assessed by a robot (which is what refer to the PopeTech application as). An example would be alt text on an image. PopeTech cannot tell if a piece of alt text is appropriate, or whether an image even needs alt text in the first place. Some things need a human.<\/p>\n\n\n\n

What\u2019s the outcome?<\/h2>\n\n\n\n

From the PopeTech scan we receive a report detailing any errors on the site. There are two ways in which to numerate the errors on a website:<\/p>\n\n\n\n