You are designing an HTML5 website. You need to design the interface such that the
content is viewable in all types of browsers, including screen readers, What should you do?
(Each correct answer presents a complete solution. Choose all that apply.)
A.
Ensure that content elements have valid and descriptive names.
B.
Use Resource Description Framework (RDF) to describe content elements.
C.
Convert HTML forms to XForms.
D.
Use HTML5 semantic markup elements.
E.
Annotate content elements with Accessible Rich Internet Application (ARIA) attributes.
Correct answers:
A, D, E
1
0
Agree
0
0
How option A will be one of the correct answers? Just giving meaningful and descriptive name will not make any change, right?
0
0
To elaborate on dwa’s comment, in the Microsoft Press book, Exam Ref 70-480: Programming in HTML5 with JavaScript and CSS3, in a section in Chapter 1 titled “Optimizing for screen readers” the author states:
“HTML5 introduced semantic elements to create new sections. This means that , , , and elements all define new sections.”
Later in that section, the author adds:
“You should explicitly define the sections by using the appropriate semantics.”
In other words, ensure that content elements have valid and descriptive names.
0
0
Darn it…
“This means that <section>, <article>, <nav>, and <aside> elements all define new sections.”
0
0
Pradeep it’s importent with names if the site are to be used with screen readers.
0
0
I think that A is incorrect, cause the question says “Each correct answer presents a complete solution”. Answer A does not present it, is only another rule to achieve accesibility.
0
0
a,d,e
0
0
A is not correct…
0
0
The name attribute of an element is used for GET or POST requests when submitting a form. It has nothing to do with accessibility. In fact, the constraints on the values of the name element (since it could wind up in your query string,) make it unsuitable for screen readers and the like.
The discussion of semantics referenced above refers to using the correct html5 element types (section, article, nav,) and *not* to those elements’ “name” attribute. You can’t just make up a descriptive element name (as opposed to name attribute value,) you’re limited to the ones defined in HTML5 (if you want accessibility software to recognize it, and because no special characters.)
If A refers to the type of element, then it’s the same as answer D – and if it refers to the name attribute, it’s wrong.
D, E.
0
0
Besides, part of that new 231Q 70-486 dumps FYI:
https://drive.google.com/open?id=0B-ob6L_QjGLpflNtUWtkNlk3ODJFY0pqOUhqVFEwc0lrd0QtamRxUHFLLUdWZEVDaGtlQWM
Best Regards!
0
0