Mixed Sample Question Flashcards
Which of the following would be the best text to put in the <title> tag of the accessibility policy page at a university with the top-level heading, “Accessibility Policy”?</title>
- Accessibility Policy | Virginia Tech
- This is a trick question; no title is necessary if a top-level heading is provided
- Virginia Tech complies with the requirements set forth under Section 508 of the Rehabilitation Act of 1973 and the Web Content Accessibility Guideline 2.0, Level A and AA
- Virginia Tech | Accessibility Policy
- Accessibility Policy | Virginia Tech
Which of the following is NOT a valid value for the lang attribute?
- en-gb
- en
- english
- es
- english
Which of the following is NOT a valid way of programmatically indicating the language of a page or content on that page?
- <blockquote language=”fr”>
- <!doctype html lang=”de”>
- <html lang=”en”>
- <span lang=”es”>
- <!doctype html lang=”de”>
What WCAG conformance level are the success criteria having to do with the language of the page and the language of parts of the page?
- The criterion having to do with the language of the page is a conformance level A requirement, while the criterion having to do with the language of parts of the page is a level AA requirement
- The criterion having to do with the language of the page and the criterion having to do with the language of parts of the page are both conformance level A requirements
- The criterion having to do with the language of the page is a conformance level AA requirement, while the criterion having to do with the language of parts of the page is a level AAA requirement
- The criterion having to do with the language of the page and the criterion having to do with the language of parts of the page are both conformance level AA requirements
- The criterion having to do with the language of the page is a conformance level A requirement, while the criterion having to do with the language of parts of the page is a level AA requirement
Why is it inadvisable to rely solely on landmark regions as a means of bypassing repetitive content?
- Landmark regions are not yet supported by all major screen readers
- Landmark regions are announced to screen reader users when encountered, but most screen readers do not provide a means for navigating between them.
- Because the accesskey attribute has made landmark regions obsolete
- Most browsers do not provide a means for sighted keyboard users to use landmark regions to bypass content
- Most browsers do not provide a means for sighted keyboard users to use landmark regions to bypass content
What is the purpose of landmark regions?
- To designate sections of the overall page design and layout
- To indicate which parts of the page can be read by screen readers
- To create focusable areas on the page
- To designate sections within content
- To designate (Kennzeich ung) sections of the overall page design and layout
Which of the following is NOT listed among landmarks by most screen readers?
- <article>
</article> - <nav>
</nav> - role=”contentinfo”
- <main>
</main>
- <article>
</article>
In a site with two regions for navigation, one for navigating the site and one for navigating a section of the site, of the following, which would be the best way to code the part of the page with the site navigation?
- <nav>
</nav> - <nav alt=”site”>
- <navigation aria-label=”site”>
- <nav aria-label=”site”>
- <nav aria-label=”site”>
Which of the following landmarks is it okay to have more than one of on a page?
- role=”main”
- role=”contentinfo”
- role=”complementary”
- role=”banner”
- role=”complementary”
Which of the following is NOT way to list all landmarks using a screen reader?
- In VoiceOver with Safari on iOS swipe up, then down
- In JAWS press Insert + F3 and then select landmarks
- In VoiceOver with Safari on macOS press Control + Option + U, then use left/right arrows to select landmarks
- In NVDA press Insert + F7 and then select landmarks
- In VoiceOver with Safari on iOS swipe up, then down
This function is not avaiable for VoiceOver on iOS
Which of the following is NOT a way to navigate from one landmark to the next using a screen reader?
- In VoiceOver with Safari on macOS, press Control + Option + L
- In Talkback, bring up the local context menu by swiping up and then right, then select landmarks, then swipe right or left
- In JAWS 16 and above, press the R key
- In NVDA, press the D key
- In VoiceOver with Safari on macOS, press Control + Option + L
The function is not available for VoiceOVer on Mac
Which of the following is a way to navigate to the main content landmark using a screen reader?
- In Talkback, swipe left, then right
- In VoiceOver on macOS, press Control + Option + M
- In NVDA, press the M key
- In JAWS, press the Q key
- In JAWS, press the Q key
for the other screenreaders the function is not available
Which of the following is NOT a benefit of using headings on web pages?
- Most browsers natively provide keyboard shortcuts that allow keyboard users to easily navigate through a document by shifting focus to properly-coded headings
- They improve search engine optimization
- They clearly communicate the structure of the document, which benefits everyone
- They allow screen reader users to easily can get a high-level overview of a web page and quickly jump to the part of the page they are interested in
- Most browsers natively provide keyboard shortcuts that allow keyboard users to easily navigate through a document by shifting focus to properly-coded headings
Which of the following is NOT a valid way of programmatically communicating that something is a heading?
- <p>A subsection of a page about headings<p>
</p></p> - <header>A page about headings</header>
- <div>A page about headings</div>
- <h1>A page about headings</h1>
- <header>A page about headings</header>
Which of the following is a reason why this code is a bad way of communicating to all users that something is a heading?
<p “font-size: 200%”><strong>A section about a topic</strong></p>
- Because, as coded, screen reader users will not be informed that the content they are encountering is a heading
- Because the <strong> tag is only used for formatting and does not communicate importance</strong>
- Because aria-level is not specified, which makes it impossible for screen reader users to know that the content is a heading
- Because setting styles inline makes it impossible for users to apply custom styles to suit their preferences
- Because, as coded, screen reader users will not be informed that the content they are encountering is a heading