New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 508565 link

Starred by 10 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

issue 477424

  • Only users with EditIssue permission may comment.

Sign in to add a comment

Make extension sidebar API accessible

Reported by, Jul 9 2015

Issue description

At the time of writing, the sidebar API doesn't exist ( bug 477424 ), but I want to get the accessibility story in place before we get too far.

Basically: the goal of this API is to move the sidebars that extensions render in-page with an official sidebar API, part of Chrome's UI. One of the benefits for this is accessibility, because the sidebar is irrelevant to the page content, but screen readers may be confused into thinking that it is.

On the other hand we do still want it so that you can descend into the sidebar (i.e. that the sidebar gets some kind of sensible accessibility tree generated for it).

Hopefully my terminology is correct here, but, is there anything we should be doing to make sure that this is sensible? By default I suppose the sidebar widget would be part of Chrome's UI and visibility to accessibility would come for free, I just want to make sure that it does so correctly, and that descending into the sidebar content (which will be extension DOM) is correct.
Blocking: chromium:477424

Comment 2 Deleted

Labels: Restrict-AddIssueComment-EditIssue
Status: WontFix
Closing this as part of  issue 477424 .

Sign in to add a comment