While this approach would be acceptable for a page with the single control (that is being auto-focused), it would be beneficial to still allow a user of assistive technology (such as a screen reader) to get full information that is visually presented on the page **before the button thus would likely to be skipped when focus is forced on the later content**. In this case, adding `aria-labeledby` on the unlabeled `<article>` element that would reference the `id` of the first heading element **and** adding `aria-describedby` referencing to the `id`s of the remaining 3 text and heading elements in this article (or even to the article itself) would allow a blind user to still know which text-only information is visually presented on the page above this autofocused control (and avoid an accessibility bug)
Bug 2021447 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
While this approach would be acceptable for a page with the single control (that is being auto-focused), it would be beneficial to still allow a user of assistive technology (such as a screen reader) to get full information that is visually presented on the page **before the button thus would likely to be skipped when focus is forced on the later content**. In this case, adding `aria-labeledby` on the unlabeled `<article>` element that would reference the `id` of the first heading element **and** adding `aria-describedby` referencing to the `id`s of the remaining 3 text and heading elements in this article (or even to the article itself) would allow a blind user to still know which text-only information is visually presented on the page above this autofocused control (and avoid an increasing the severity of the accessibility bug and blocking users from the important information about **why** they're "trying again").