-
Ensure any frames and iframes provide a title attribute that describes the purpose of the frame. People using assistive technology such as a screen reader can then determine whether to navigate into the frame or skip it. https://www.w3.org/WAI/WCAG21/Techniques/html/H64 …
#Accessibility#A11y#A11yAdvice pic.twitter.com/R2xsqc7pjC
-
Identify the default language of a web page by providing the lang attribute on the html element. This assists assistive technology in properly announcing and interpreting content on a page. https://www.w3.org/WAI/WCAG21/Techniques/html/H57 …
#Accessibility#A11y#A11yAdvice pic.twitter.com/pHbxnL5syZ
-
If your web site is more than a few years old, check your code for bad practices, such as using white space characters to simulate multiple columns. https://www.w3.org/WAI/WCAG21/Techniques/failures/F33 …
#Accessibility#A11y#A11yAdvice pic.twitter.com/4J0YCceBdF
-
Un-fix your sticky headers and footers via media queries when the screen does not provide enough room to view the content (mobile dimensions in landscape orientation, zoomed in). https://www.w3.org/WAI/WCAG21/Techniques/css/C34 …
#Accessibility#A11y#A11yAdvice pic.twitter.com/2HSURFFrQV
-
Each link that opens a new browser window or tab must communicate this to assistive technology, such as screen readers, as part of the link text. https://www.w3.org/WAI/WCAG21/Techniques/html/H83 …
#Accessibility#A11y#A11yAdvice pic.twitter.com/2QrSIf2i2v
-
All table th elements should have a scope attribute. While screen readers may correctly guess whether a header is a header for a column or row, assigning a scope makes this explicit. https://www.w3.org/WAI/WCAG21/Techniques/html/H63 …
#Accessibility#A11y#A11yAdvice pic.twitter.com/wbXoLYNwYY
-
Validate your code, ensuring it is coded to HTML specification. Parsing issues, such as improperly nested and unclosed elements, missing or duplicate ids, etc. can impact accessibility. https://www.w3.org/WAI/WCAG21/Techniques/html/H88 … Validate: http://validator.w3.org/
#Accessibility#A11y#A11yAdvice pic.twitter.com/BXrpbT3M6Z
-
Ensure that controls and features are labelled consistently across pages on a web site. https://www.w3.org/WAI/WCAG21/Techniques/failures/F31 …
#Accessibility#A11y#A11yAdvice pic.twitter.com/Qr7UCtDEJc
-
Do you have groups of images and text links and multiple instances of links referencing the same URL? Combine them to reduce duplication, which can be laborious for people using a screen reader. https://www.w3.org/TR/WCAG20-TECHS/H2.html …
#Accessibility#A11y#A11yAdvice pic.twitter.com/Oyd8J7PykG
-
Do you present elements or features that automatically move, blink or update? Add a control that stops the motion or updates, which can present issues for some people. https://www.w3.org/TR/WCAG20-TECHS/G186.html …
#Accessibility#A11y#A11yAdvice pic.twitter.com/QHwrsq4p09
-
Business West members: Few places left on our An Evening with Nomensa http://bit.ly/pfEMUH
#UXAdvice#A11yAdvice
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.