DescriptionThis rule checks that image elements that use their source filename as their accessible name do so without loss of information to the user. Show
ApplicabilityThis rule applies to any HTML element that is
included in the accessibility tree and has a non-empty (
When comparing accessible name and filename, difference in letter casing, leading and trailing whitespace should be ignored. ExpectationEach test target has an accessible name that serves an equivalent purpose to the non-text content. If there are several image sources, then the accessible name must accurately describe all of them. AssumptionsThere are currently no assumptions Accessibility SupportThere are no major accessibility support issues known for this rule. BackgroundIt is fairly common for content management systems (CMS) or other tools to default the alt-text of an image to its filename if no alt-text is provided. However, these names are usually not descriptive (often due to the presence of the file extension). This rule uses this heuristic to pinpoint cases where the accessible name should be looked at by human testers. This rule does not automatically decide in which case a filename is correct (notably, it does not automatically decide whether adding the file extension is acceptable). Bibliography
Accessibility Requirements Mapping
Input AspectsThe following aspects are required in using this rule.
Test CasesPassedPassed Example 1Open in a new tab This
Passed Example 2Open in a new tab This
Passed Example 3Open in a new tab This image button has an accessible name equivalent to the filename. The accessible name accurately describes the purpose of the button.
Passed Example 4Open in a new tab This
Passed Example 5Open in a new tab This
Passed Example 6Open in a new tab This
FailedFailed Example 1Open in a new tab This
Failed Example 2Open in a new tab This
Failed Example 3Open in a new tab This
Failed Example 4Open in a new tab This image button has an accessible name matching the filename. The presence of the file extension in the accessible name is confusing and results in the accessible name not accurately describing the image.
Failed Example 5Open in a new tab This
InapplicableInapplicable Example 1Open in a new tab This
Inapplicable Example 2Open in a new tab This
Inapplicable Example 3Open in a new tab This
Inapplicable Example 4Open in a new tab This
GlossaryAccessible NameThe accessible name is the programmatically determined name of a user interface element that is included in the accessibility tree. The accessible name is calculated using the accessible name and description computation. For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in HTML Accessibility API Mappings 1.0, Accessible Name and Description Computation (working draft) and SVG Accessibility API Mappings, Name and Description (working draft). For more details, see examples of accessible name. Note: As per the accessible name and description computation, each element always has an accessible name. When no accessible name is provided, the element will nonetheless be assigned an empty ( Note: As per the accessible name and description computation, accessible names are flat string trimmed of leading and trailing whitespace. Notably, it is not possible for a non-empty accessible name to be composed only of whitespace since these must be trimmed. Explicit Semantic RoleThe explicit semantic role of an element is determined by its role attribute (if any). The role attribute takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from WAI-ARIA Specifications. If the element has no role attribute, or if it has one with no valid role, then this element has no explicit semantic role. Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the accessibility support base line. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. FilenameA filename is a text string that identifies an electronically stored file. In a URL it is located at the end of the path, after the last slash and before any query strings. For example the FocusableAn element is focusable if one or both of the following are true:
Exception: Elements that lose focus during a period of up to 1 second after gaining focus, without the user interacting with the page the element is on, are not considered focusable. Notes:
Implicit Semantic RoleThe implicit semantic role of an element is a pre-defined value given by the host language which depends on the element and its ancestors. Implicit roles for HTML and SVG, are documented in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft). Included in the accessibility treeElements included in the accessibility tree of platform specific accessibility APIs are exposed to assistive technologies. This allows users of assistive technology to access the elements in a way that meets the requirements of the individual user. The general rules for when elements are included in the accessibility tree are defined in the core accessibility API mappings. For native markup languages, such as HTML and SVG, additional rules for when elements are included in the accessibility tree can be found in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft). For more details, see examples of included in the accessibility tree. Programmatically hidden elements are removed from the accessibility tree. However, some browsers will leave focusable elements with an Marked as decorativeAn element is marked as decorative if one or more of the following conditions is true:
Elements are marked as decorative as a way to convey the intention of the author that they are pure decoration. It is different from the element actually being pure decoration as authors may make mistakes. It is different from the element being effectively ignored by assistive technologies as rules such as presentational roles conflict resolution may overwrite this intention. Elements can also be ignored by assistive technologies if they are programmatically hidden. This is different from marking the element as decorative and does not convey the same intention. Notably, being programmatically hidden may change as users interact with the page (showing and hiding elements) while being marked as decorative should stay the same through all states of the page. Namespaced ElementAn element with a specific namespaceURI value from HTML namespaces. For example an
“SVG element” is any element with the “SVG namespace”, which is Namespaced elements are not limited to elements described in a specification. They also include custom elements. Elements such as OutcomeAn outcome is a conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:
Note: A rule has one Note: Implementations using the EARL10-Schema can express the outcome with the outcome property. In addition to Programmatically HiddenAn HTML element is programmatically hidden if either it has a
computed CSS property
Note: Contrary to the other conditions, the Note: The
HTML standard suggests setting the CSS Semantic RoleThe semantic role of an element is determined by the first of these cases that applies:
This definition can be used in expressions such as “semantic WAI-ARIA specificationsThe WAI ARIA Specifications group both the WAI ARIA W3C Recommendation and ARIA modules, namely:
Note: depending on the type of content being evaluated, part of the specifications might be irrelevant and should be ignored. WhitespaceWhitespace are characters that have the Unicode “White_Space” property in the Unicode properties list. This includes:
Rule VersionsThis is the first version of this ACT rule. ImplementationsThere are currently no known implementations for this rule. If you would like to contribute an implementation, please read the ACT Implementations page for details. Which statement accurately describes the act of setting expectations for others quizlet?Which of the following accurately describes the act of setting expectations for others? Setting expectations is directly tied to your ability to foster interpersonal trust in the workplace.
What is a component of setting expectations quizlet?Three components are central in setting expectations for those you manage: describing responsibilities, providing deadlines, and discussing coordination.
What is the foremost requirement of an expression of sympathy?The foremost requirement of any expression of sympathy is that it be sincere.
What can you do to encourage employees to read announcements quizlet?What can you do to encourage employees to read announcements? Use a specific, catchy subject line that creates interest. ensure the tone of the message is reader-centered. Read the following request, which Shana sent to her supervisor.
|