Skip to content

Update where setSemanticsEnabled is found on 'Accessibility' page #8686

Closed

Description

@dmosdallas

Page URL

https://docs.flutter.dev/accessibility-and-localization/accessibility/

Page source

https://github.com/flutter/website/tree/main/src/accessibility-and-localization/accessibility.md

Describe the problem

Under Screen Readers --> Browser, this page states:

Screen Readers users on web will need to toggle “Enable accessibility” button to build the semantics tree. Users can skip this step if you programmatically auto-enable accessibility for your app using this API:

RendererBinding.instance.setSemanticsEnabled(true)

However, it looks like the setSemanticsEnabled function is no longer a part of RendererBinding in flutter 3.10

Expected fix

Guide should provide up-to-date details on how to programmatically auto-enable accessibility for an app.

Additional context

No response

Activity

  1. danagbemava-nc commented on May 15, 2023

    @danagbemava-nc
    Member

    It looks like this was moved to the SemanticsBinding class instead. See flutter/flutter#121289

    Thanks for pointing this out

  2. added
    p2-mediumNecessary but not urgent concern. Resolve when possible.
    and removed
    st.triage.triage-teamTriage team reviewing and categorizing the issue
    on May 15, 2023
  3. changed the title [-][PAGE ISSUE]: 'Accessibility'[/-] [+]Update where `setSemanticsEnabled` is found on 'Accessibility' page[/+] on May 17, 2023
  4. added
    t.a11yRelates to an accessibility concern
    and removed on May 17, 2023
  5. self-assigned this
    on May 17, 2023
  6. aakashawalkar commented on May 18, 2023

    @aakashawalkar

    Solution:
    For Flutter 3.10.0, Replace RendererBinding.instance.setSemanticsEnabled(true); with SemanticsBinding.instance.ensureSemantics();

  7. added a commit that references this issue on Jun 9, 2023
    8cc72c0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

e0-minutesEffort: < 60 minp2-mediumNecessary but not urgent concern. Resolve when possible.t.a11yRelates to an accessibility concern

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions