Closed Bug 1392753 Opened 7 years ago Closed 7 years ago

Create SUMO article to help with and explain Accessibility features/services.

Categories

(support.mozilla.org :: Knowledge Base Content, task, P1)

Tracking

(firefox57+ fixed)

RESOLVED FIXED
2017Q3
Tracking Status
firefox57 + fixed

People

(Reporter: yzen, Unassigned)

References

()

Details

(Whiteboard: aes+)

In scope for Firefox 57 we are adding an accessibility indicator (bug 1383051) that will be visible in the titlebar/tabbar similar to private browsing indicator; we are also adding a privacy preference related to accessibility (bug 1384567) that allows third party accessibility services to access Firefox.

The preference will have a Learn more link that will point to the SUMO page explaining implications of allowing or restricting access to accessibility services, its effect on performance and memory footprint.

Similarly, when accessibility indicator is visible (meaning Firefox accessibility features are active) a user would be able to click on the indicator and navigate to the above SUMO page.

In addition that page would inform users on how to check what accessibility service has requested accessibility features in order to make an informed decision to disable accessibility or keep it enabled.
I think if we had a URL for the article, not the article itself, the features in the blocked bugs could land.
Flags: needinfo?(jsavage)
Component: General → Knowledge Base Content
Product: Firefox → support.mozilla.org
I've started putting bullet points together for this sumo page. Welcome edits from everyone.
No longer blocks: 1384567
Depends on: 1384567
Whiteboard: aes+
Depends on: 1393987
I believe the URL is https://support.mozilla.org/en-US/kb/accessibility-services . Still being reviewed but I think it is reserved.
Ok I think that doc is complete now. Joni over to you. FYI this feature is targeting 57 rollout.

The url for the Learn more link is (copied from my nightly):

https://support.mozilla.org/1/firefox/57.0a1/WINNT/en-US/accessibility
Flags: needinfo?(jsavage)
Target Milestone: --- → 2017Q3
Oops, sorry.
Flags: needinfo?(jsavage)
(In reply to Yura Zenevich [:yzen] from comment #3)
> I believe the URL is
> https://support.mozilla.org/en-US/kb/accessibility-services . Still being
> reviewed but I think it is reserved.

I made a few small revisions to the article and approved it. I didn't mark it ready to localize since Joni Savage may want to make additional revisions.
I think the description box under "My Accessibility Services indicator is visible, what does this mean?" needs some sort of header or explanation. That data doesn't seem connected to the "find this entry in about:support" text. Other than that, lgtm!
(from comment #7)
> I think the description box under "My Accessibility Services indicator is
> visible, what does this mean?" needs some sort of header or explanation.
> That data doesn't seem connected to the "find this entry in about:support"
> text. Other than that, lgtm!

To Joni: Can you review the https://support.mozilla.org/en-US/kb/accessibility-services SUMO KB article? 

Also, the Learn more link https://support.mozilla.org/1/firefox/57.0a1/WINNT/en-US/accessibility (copied from my nightly) should go to the SUMO KB article but instead I get a "Page Not Found".
[Tracking Requested - why for this release]:
sumo article bug for a feature shipping in 57.
I caught this nit just now: users on Mac and Linux won't get instantiator info in about:support, so https://support.mozilla.org/en-US/kb/accessibility-services#w_my-accessibility-services-indicator-is-visible-what-does-this-mean might confuse those users.
(I mean instantiator client info)
Thanks for putting the content together, and Alice, thank you for publishing it. I've set up the in-product URL on our end now to redirect to the article.

I've also marked it for localization.

(Thanks to Noah too, for bringing this to my attention).
Flags: needinfo?(jsavage)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Depends on: 1408113
You need to log in before you can comment on or make changes to this bug.