0

Don't offer Reader Mode when in Slack

 3 months ago
source link: https://bugzilla.mozilla.org/show_bug.cgi?id=1589007
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Closed Bug 1589007 Opened 4 years ago Closed 1 month ago

Don't offer Reader Mode when in Slack

Categories

(Toolkit :: Reader Mode, defect, P3)

Tracking

(bug RESOLVED as FIXED)

RESOLVED FIXED

123 Branch

Accessibility Severity s3
Tracking Status
firefox-esr115 --- wontfix
firefox71 --- wontfix
firefox121 --- wontfix
firefox122 --- wontfix
firefox123 --- fixed

People

(Reporter: MarcoZ, Assigned: ini, Mentored)

References

Details

Ever since Jamie fixed bug 1585907, screen reader users are more aware when reader mode is offered. However, reader mode seems to be offered in contexts where it does not make much sense, like when in an application like Slack. While some parts of it might warrant reader mode, since reader mode applies to the whole page/application UI, it does not make sense to offer it in these circumstances.

Whiteboard: [Access:p2] → [access-p2]

Updating the Accessibility Team's impact assessment to conform with the new triage guidelines. See https://wiki.mozilla.org/Accessibility/Triage for descriptions of these whiteboard flags.

Whiteboard: [access-p2] → [access-s3]
Severity: normal → S3
Accessibility Severity: --- → s3
Whiteboard: [access-s3]

I think the most straightforward fix would be to add Slack to the blocked hosts list, similar to bug 1210366.

Assignee: nobody → cmeador
Mentor: cmeador
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in before you can comment on or make changes to this bug.

report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK