It\u2019s recommended to use HTML tables only for tabular data. Avoid using HTML tables for layout purposes. When implementing HTML tables use row and column headers, and associate data cells with header cells on complex tables.<\/p>\n
Required:<\/strong> Identify row and column headers with the th tag.<\/p>\nRecommended:<\/strong> <\/em>Do not use HTML tables for page or content layout.<\/p>\nRecommended:<\/strong><\/em> Use the summary attribute to explain the purpose and structure of the table.<\/p>\nRecommended:<\/strong><\/em> Use the caption element to provide a descriptive title of the table.<\/p>\nRequired:<\/strong> Simple HTML tables (tabular data) have scope (row or col) set on table header cells.<\/p>\nRecommended:<\/strong><\/em> Complex HTML tables (those with multiple rows, column spans, etc.) use headers and id attributes to associate data cells with header cells.<\/p>\nWCAG 2.0 Reference: Guideline 1.3.2<\/span>
\n<\/div>\n<\/div>\n\n<\/div>\n\n
Checkpoint 8: Frames \/ iframes<\/h5>Frames or iframes (in-line frames) should be titled for help with identification and navigation.<\/p>\n
Required:<\/strong> Frames\/iframes use the title attribute identifying their purpose and describing their content.<\/p>\nRecommended:<\/strong> <\/em>Do not use hidden frames or hidden iframes.<\/p>\nRecommended:<\/strong><\/em> Use CSS or iframes (in-line frames) rather than standard HTML frames.<\/p>\nWCAG 2.0 Reference: Guideline 1.3<\/span>
\n<\/div>\n<\/div>\n\n<\/div>\n\n
Checkpoint 9: Keyboard Navigation and Focus<\/h5><\/p>\n
Not all visitors can use a mouse, touchpad, or other point-and-click device. Make all functionality available from a keyboard.<\/p>\n
Required:<\/strong> Visitors must be able to move focus on the page using a keyboard interface, typically using arrow or tab keys. (This is included by default in BU Responsive Framework WordPress theme.)<\/p>\nRequired:<\/strong> If keyboard navigation requires more than unmodified arrow or tab keys or other standard methods, the visitor is advised of the method for moving focus.<\/p>\nRequired:<\/strong> Web-based forms must support assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. (Standard forms created with the forms plugin and BU Responsive Framework WordPress theme meet accessibility guidelines.)<\/p>\nRecommended:<\/strong><\/em> Ensure tab order for web-based forms moves the visitor through the form in a logical manner (e.g. first name followed by last name; field labels correspond to their form elements, etc.)<\/p>\nWCAG 2.0 Reference: Guideline 2.1<\/span>
\n<\/div>\n<\/div>\n\n<\/div>\n\n
Checkpoint 10: Seizures<\/h5>Pages should be designed to avoid causing the screen to flash more than three times in any one second. Flashing content at certain frequencies is known to cause seizures in some individuals.<\/p>\n
Required:<\/strong> Do not publish content that flashes 3 times or more in any one second, or the flash is below the general flash and red flash thresholds.<\/p>\nWCAG 2.0 Reference: Guideline 2.3<\/span>
\n<\/div>\n<\/div>\n\n<\/div>\n\n
Checkpoint 11: Navigation and Wayfinding<\/h5>Provide a method for visitors to skip over long lists of links, such as primary content navigation menus. Clearly identify link targets and inform the user when links open in pop-ups or new windows.<\/p>\n
Required:<\/strong> Provide a way for users to skip repetitive link lists (e.g. \u201cskip to page content\u201d).<\/p>\nRequired:<\/strong> Styles should accommodate clear visibility of the keyboard focus indicator. (This is included by default in BU Responsive Framework WordPress theme.)<\/p>\nRequired:<\/strong> Do not use styles to remove the underline from text links unless there is another way of visually distinguishing clickable text without relying solely on text color.<\/p>\nRequired:<\/strong> Do not use \u201cclick here\u201d or \u201chere\u201d for link text. Identify the target of each link, preferably within the context of the link language itself.<\/p>\nRequired:<\/strong> To accommodate users of touch devices, navigation icons\/buttons must use a minimum touch-target size of 48 pixels x 48 pixels.<\/p>\nRecommended:<\/strong><\/em> Use ARIA landmark roles. (This is included by default in BU Responsive Framework WordPress theme.)<\/p>\nRecommended:<\/strong> <\/em>Do not change the active window without informing the user.<\/p>\nWCAG 2.0 Reference: Guideline 2.4<\/span>
\n<\/div>\n<\/div>\n\n<\/div>\n\n
Checkpoint 12: Adequate Time for Tasks.<\/h5>Ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit.<\/p>\n
Required:<\/strong> When a time limit is set by content, provide visitors with at least one of following mechanisms:<\/p>\n\n- Visitor is allowed to turn off the time limit.<\/li>\n
- Visitor can adjust the time limit.<\/li>\n
- Visitor is given an accessible mechanism to extend the time limit when the limit is reached.<\/li>\n
- Exceptions: real-time events (e.g. online auction) and activities where the time limit is an essential function.<\/li>\n<\/ul>\n
Required:<\/strong> Do not used timed server redirects.<\/p>\nWCAG 2.0 Reference: Guideline 2.2<\/span>
\n<\/div>\n<\/div>\n\n<\/div>\n\n
Checkpoint 13: An Understandable User Experience<\/h5><\/p>\n
Content and information plus the operation of user interface must be understandable. Pages should appear and operate in predictable ways.<\/p>\n
Required:<\/strong> The language of the page and language of the content can be programmatically determined. (This is included by default in BU Responsive Framework WordPress theme for pages published in the English language; editors of sites using non-English languages can configure custom meta tags to define the native language for their pages.)<\/p>\nRequired:<\/strong> Navigational mechanisms that are repeated on multiple pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (This is included by default in BU Responsive Framework WordPress theme.)<\/p>\nWCAG 2.0 Reference: Guidelines 3.1, 3.2<\/span>
\n<\/div>\n<\/div>\n\n<\/div>\n\n
Checkpoint 14: Best Practices and Standards Compliance<\/h5><\/p>\n
Follow web best practices and use standards-compliant markup for all content.<\/p>\n
Required:<\/strong> All user interface components (including form elements, links and components generated by scripts) can be programmatically determined by assistive technologies. (This is included by default in BU Responsive Framework WordPress theme.)<\/p>\nRequired:<\/strong> When using hand-crafted HTML ensure all elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique.<\/p>\nRequired:<\/strong> Provide error feedback for web-based forms (e.g. when a required field is missing, alert the user in a manner consumable by assistive technologies).<\/p>\nRecommended:<\/em><\/strong> Use an accessible publishing system (e.g. BU Responsive Framework WordPress theme) and use hand-crafted HTML responsibly and work with professionally-trained web developers experienced with accessibility concerns.<\/p>\nWCAG 2.0 Reference: Guidelines 3.3, 4.1<\/span>
\n<\/div>\n<\/div>\n\n<\/div>\n<\/p>\n
Last Resort<\/h5>\n
An accessible alternate page (e.g. text-only, non-Flash, non-dynamic, etc.) mirroring equivalent information or functionality, can be provided to make a web site comply with this policy, when compliance cannot be accomplished in any other way. The content of mirror pages must be updated every time the primary page changes. Separate, up-to-date, accessible \u201cmirror pages\u201d are used only as a last resort.<\/strong><\/p>\n<\/p>\n<\/div>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Under the University\u2019s Website Policy (the \u201cPolicy\u201d), all new and redesigned University Websites and Web-enabled content published after the Policy\u2019s Effective Date must comply with these Minimum Web Accessibility Standards (MWAS). The MWAS articulate the minimum technical and visual requirements needed to comply with the Policy\u2019s accessibility requirements for University Websites and Web-enabled content. Capitalized […]<\/p>\n","protected":false},"author":8,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-templates\/no-sidebars.php","meta":[],"_links":{"self":[{"href":"https:\/\/www.bu.edu\/mwas\/wp-json\/wp\/v2\/pages\/5"}],"collection":[{"href":"https:\/\/www.bu.edu\/mwas\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.bu.edu\/mwas\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/mwas\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/mwas\/wp-json\/wp\/v2\/comments?post=5"}],"version-history":[{"count":24,"href":"https:\/\/www.bu.edu\/mwas\/wp-json\/wp\/v2\/pages\/5\/revisions"}],"predecessor-version":[{"id":68,"href":"https:\/\/www.bu.edu\/mwas\/wp-json\/wp\/v2\/pages\/5\/revisions\/68"}],"wp:attachment":[{"href":"https:\/\/www.bu.edu\/mwas\/wp-json\/wp\/v2\/media?parent=5"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Accessibility](\"\/mwas\/files\/2018\/07\/big-blue-vman.svg\")
<\/div>\n