Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editorial tweaks to object name rule #2218

Merged
merged 3 commits into from
Jan 16, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions _rules/object-has-accessible-name-8fc3b6.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,11 +50,7 @@ The [MIME type][] of the resource embedded in the `data` attribute impacts how t

Testing that the [accessible name][] describes the purpose of the `object` element is not part of this rule and must be tested separately.

Non-supported media formats make screen readers render the text content of the element instead of other attributes.

`Object` elements without an accessible name are ignored by assistive technologies unless they have an [explicit role][].

When the object resource is not loaded, the fallback content is rendered as shown in the Inapplicable Example: "This `object` element does not need an accessible name because it loads no image, audio, or video."
When the object resource is not loaded, the fallback content is rendered as shown in the Inapplicable Example: "This `object` element does not need an accessible name because it loads no image, audio, or video.". When screen readers encounter an unsupported media format they will also use the fallback content instead of other attributes.
WilcoFiers marked this conversation as resolved.
Show resolved Hide resolved

### Bibliography

Expand Down
Loading