![]() An accessibility statement, detailing any accessibility issues and who to contact if there is a problem, should be published for each website and app. 2) Accessibility Regulations 2018 requires public sector organisations to make their websites and mobile apps accessible. How Knowbility promotes employment for people with disabilities Exploring WCAG 2.1 - 1.4.The Public Sector Bodies (Websites and Mobile Applications) (No. Exploring WCAG 2.1 - 2.1.4 Character Key Shortcuts.Exploring WCAG 2.1 - 2.5.4 Motion Actuation.Exploring WCAG 2.1 - 2.5.3 Label in Name. ![]() Exploring WCAG 2.1 - 2.5.2 Pointer Cancellation.Exploring WCAG 2.1 - 2.5.1 Pointer Gestures.Welcome, WCAG 2.1! The Web Content Accessibility Guidelines get an update. ![]() Do not rely on fixed size containers and let elements reflow on the page. TakeawaysĪs we have seen with other new WCAG 2.1 success criteria, responsive design helps to meet the text spacing requirements. People with dyslexia, reading, or other cognitive disabilities may have specific spacing requirements. This includes people with low vision who use a bigger font. Who Benefits?Īnyone who needs to change the font or text display properties to read the content will benefit. The Understanding Success Criterion 1.4.12: Text Spacing document has more examples. There is a picture and headline text for each item. The screen shot below shows a section of a news page containing two columns and three rows of news story headlines. The best way to support this success criterion is to use responsive design and not use containers with fixed height or width. ![]() Text implemented using the canvas element is also exempt because it is considerd images of text. Video captions, images of text, and logos are not covered. Since PDF is not a markup language, it is not covered by this rule. The wording of the success criterion specifies content created using markup languages. But, the page must reflow properly when these settings do change so that all content is still visible. The web page author is not required to provide options to change these settings. The user would adjust these values using a custom style sheet, extension, bookmarklet, or browser settings. People with cognitive or reading disabilities may read better when there is more space between letters, words, lines, or paragraphs. Testing a site by changing the letter, word, or line spacing can simulate the effect of using larger fonts. People with low vision often use a much larger default font. The intent of this success criterion is to allow people to modify text to make it easier to read. Word spacing to at least 0.16 times the font size.Įxception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.Letter spacing (tracking) to at least 0.12 times the font size.Spacing following paragraphs to at least 2 times the font size.Line height (line spacing) to at least 1.5 times the font size.In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Make it easier for users to see and hear content including separating foreground from background. This new vision related success criteria also falls under guideline 1.4. Our series on the new WCAG 2.1 Success Criteria continues with another level AA criteria aimed at low vision, 1.4.12 Text Spacing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |