Skip to content

Instantly share code, notes, and snippets.

@matt-dray
Created July 13, 2018 19:00
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save matt-dray/921a77981c95cdbb55acb206c5167dd2 to your computer and use it in GitHub Desktop.
Save matt-dray/921a77981c95cdbb55acb206c5167dd2 to your computer and use it in GitHub Desktop.
Accessibility report from Tenon web service for https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/
bpID certainty errorDescription errorSnippet errorTitle issueID position priority ref resultTitle signature standards tID viewPortLocation xpath url
1 100 All images need an `alt` attribute. If you do not supply an `alt` attribute, that'll mean that users who ca not see the image will not understand what the image conveys. Make sure that the `alt` attribute value is a useful, concise, and clear description of the image. <img src="/images/hugo-logo.png" width="22" height="22"> This image is missing an `alt` attribute. 9b8bacf51f4a8ca12088ea7f9127f620 column: 77 , line: 197 97 https://tenon.io/bestpractice.php?bpID=1&tID=9 Provide an alt attribute for each `&lt;img&gt;` element. 0b423978ffbad8c6f96648e1938f17eb Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 1.1.1 Non-text Content 9 {"bottom-right":{"x":612.484375,"y":9819.96875},"height":22,"top-left":{"x":590.484375,"y":9797.96875},"width":22} /html/body/div[1]/footer[1]/ul[1]/li[2]/a[1]/img[1] https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/
53 100 Frames need a `title` attribute that describes the frame's content or purpose. Add a `title` attribute to the `&lt;frame&gt;` element for that. Even if the frame does not have content that is relevant to users, the frame's `title` should say that. If you do not, assistive technologies will simply announce the frame's URL to users. <iframe style="display: none;"></iframe> This frame does not have a `title` attribute. 2743a0c981a7d5ae63679b0a0e2944e1 column: 3 , line: 218 91 https://tenon.io/bestpractice.php?bpID=53&tID=13 Provide clear and informative titles for all frames and iframes. 387c4aa911526835998d14041f8ca4f0 Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 2.4.1 Bypass Blocks 13 {"bottom-right":{"x":300,"y":150},"height":150,"top-left":{"x":0,"y":0},"width":300} /html/body/iframe[1] https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/
61 100 The `alt` attribute on this image is very long. Alt attribute values should be a clear, concise, and accurate alternative to the information they're conveying. <img src="https://accessibility.blog.gov.uk/wp-content/uploads/sites/52/2016/08/Karwai-blog-1-1.png" alt="Thumbnail views of example posters including designing for users on the autistic spectrum, for users of screen readers and for users with low vis This image's `alt` attribute might not be suitable. 76e06596d322b299abe43a96ab4953e7 column: 16 , line: 131 97 https://tenon.io/bestpractice.php?bpID=61&tID=45 Make sure that each image's alternate text is clear and informative. 0ee0267e5c6bae794b7e3bc2692f6d86 Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 1.1.1 Non-text Content 45 {"bottom-right":{"x":862,"y":7261.6875},"height":631,"top-left":{"x":162,"y":6630.6875},"width":700} /html/body/div[1]/main[1]/article[1]/div[1]/div[10]/p[3]/img[1] https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/
142 60 This text appears to be styled to look like a heading. If this text is meant to be a heading, use heading markup. Doing so will add semantic value to this text, which will let users understand the content's structure. <strong>Sometimes accessibility is seen as pass/fail thing. But can you actually make services accessible for <em>everyone</em>?</strong> This may be an implicit heading. 1563a79db2f657cf7596066678caa825 column: 16 , line: 136 82 https://tenon.io/bestpractice.php?bpID=142&tID=20 Use appropriate markup for headings. Don't use heading markup for any text that isn't a heading. f1ed547282437b1554a7e32d0b4bd62f Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 1.3.1 Info and Relationships,Web Content Accessibility Guidelines (WCAG) 2.0, Level AAA: 2.4.10 Section Headings,Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 4.1.2 Name, Role, Value 20 {"bottom-right":{"x":832,"y":7495.328125},"height":59,"top-left":{"x":162,"y":7436.328125},"width":670} /html/body/div[1]/main[1]/article[1]/div[1]/div[11]/p[2]/strong[1] https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/
142 60 This text appears to be styled to look like a heading. If this text is meant to be a heading, use heading markup. Doing so will add semantic value to this text, which will let users understand the content's structure. <strong>Does government have a relationship with producers of assisitve technology?</strong> This may be an implicit heading. e79d35e9b625f5face94dad8f6a4e45b column: 16 , line: 140 82 https://tenon.io/bestpractice.php?bpID=142&tID=20 Use appropriate markup for headings. Don't use heading markup for any text that isn't a heading. 5609449d731a93e48d8d63b32d28280b Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 1.3.1 Info and Relationships,Web Content Accessibility Guidelines (WCAG) 2.0, Level AAA: 2.4.10 Section Headings,Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 4.1.2 Name, Role, Value 20 {"bottom-right":{"x":777,"y":7969.328125},"height":59,"top-left":{"x":162,"y":7910.328125},"width":615} /html/body/div[1]/main[1]/article[1]/div[1]/div[11]/p[6]/strong[1] https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/
142 60 This text appears to be styled to look like a heading. If this text is meant to be a heading, use heading markup. Doing so will add semantic value to this text, which will let users understand the content's structure. <strong>What things can we focus on immediately?</strong> This may be an implicit heading. 79c813c48499563889996efdceaa5ee7 column: 16 , line: 142 82 https://tenon.io/bestpractice.php?bpID=142&tID=20 Use appropriate markup for headings. Don't use heading markup for any text that isn't a heading. 1f490dac8591d080352766cf04654127 Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 1.3.1 Info and Relationships,Web Content Accessibility Guidelines (WCAG) 2.0, Level AAA: 2.4.10 Section Headings,Web Content Accessibility Guidelines (WCAG) 2.0, Level A: 4.1.2 Name, Role, Value 20 {"bottom-right":{"x":570,"y":8189.328125},"height":25,"top-left":{"x":162,"y":8164.328125},"width":408} /html/body/div[1]/main[1]/article[1]/div[1]/div[11]/p[8]/strong[1] https://www.rostrum.blog/2018/05/12/accessibility-workshop-at-sprint18/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment