This is an automated scan of public Web pages at NC State University. The results of the scan are available to the Web site owners. The scan report includes the following for the pages in each site.
- Accessibility errors
- Based on WCAG 2 and Section 508
- Uses two different evaluation tools for assessing a site’s accessibility
- WAVE – this tool analyzes the rendered page (DOM) and shows errors graphically within the context of the page
- SortSite – this tool primarily analyzes the source code of pages and reports the errors as line numbers
- Prioritized in terms of impact on users and frequency of occurrence
- Seeing the errors graphically in the context of the page
- Line numbers in the source code where the error occurs
- Guides for how to fix the problems
- Broken links
- Spelling errors
- Coding errors
- Usability recommendations
- Browser compatibility errors
- A ranking of how accessible each site is compared to others on campus
Icon Legend for the Reports
- Issue viewable in the source code
- Issue viewable in the context of the page
- Accessibility error
- Accessibility warning – it cannot be automatically determined if it is an error.
What to keep in mind when viewing this data
- If you have a question about one of the accessibility errors, before you invest 20 hours of time trying to fix it, ask first.
- It is more important to correct pages with current information. Pages that contain historic data, like old meeting minutes or news stories, should be a lower priority than current and new pages. Historic pages can be left in their current state until someone requests that they be made accessible.
- The only pages that are scanned are non-password protected pages that can be reached within three links of the home page.
- It’s OK to break some rules. You just need a good reason for doing it.
- These scans cannot test some aspects of accessibility, particularly how users interact with a page.
- These scans will sometimes report false positives.
- Because this scan combines the results from two different scanning tools many of the errors will show up twice, once in each report. If you fix the error the problem will disappear from both reports. Because of the way the scanning tools report the errors, it is too difficult to reconcile the two scan reports to only show you one instance of an error.
- When viewing the errors graphically within the context of the page
- the screen may not always scroll correctly to the location of the error
- the error may not be viewable on the screen if other CSS rules are hiding content on the page
- When viewing the line numbers where errors occur, sometimes the line numbers can be off. They are usually off for the following reasons.
- The content of the page has been updated since the scan was last completed.
- An error in a template will create a high occurrence of that error in your site, thus reducing your ranking. However, fixing an error in your template will greatly increase your accessibility ranking.
- You can request your site be rescanned. When the request is received, it will be added to the queue. Depending on the number of other scans in the queue and the size of your scan, it could be ready in as few as 30 minutes. You will receive an email notification when it is ready.
- Only the accessibility errors are used in determining your rank.
- There are a number of different accessibility rankings.
- Total Weighted Errors – a sum of the site’s weighted errors (smaller sites tend to rank higher)
- Weighted Errors Per Page – the average number of weighted errors per page for a site (larger sites tend to rank higher)
- Overall Accessibility Rank – the square of the sum of weighted errors divided by the total number of pages for a site (balances comparing small and large sites)
- Combined Ranking – an average of the Overall Accessibility Rank from both SortSite and WAVE
- The rankings are an approximation of how accessible your site is compared to others on campus. These scans cannot fully asses how accessible a site is. Even so, don’t you want to be number 1?
- A function to be able to exclude certain errors because they either don’t apply in a particular case you it is a false positive. Excluding an error will improve your score. An exclusion will be good for one year, at which time you must go back and confirm that those exclusions still apply and that no new errors have been generated.
- A way to improve your accessibility score by performing manual tests that the automated scan cannot perform. Each manual test performed will improve your score.
- Number of sites scanned: 511
- Number of pages scanned: 208,884