Open Bug 2077267 Opened 1 month ago Updated 17 hours ago

Run speedometer tests with accessibility enabled

Categories

(Core :: Disability Access APIs, task)

task

Tracking

()

People

(Reporter: morgan, Assigned: morgan)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

Attachments

(1 external file)

We have in-tree Raptor tests that benchmark us for speedometer. It'd be interesting to run the speedometer tests with accessibility enabled to asses performance.

The Raptor harness does not currently support a11y instantiation or awaiting/responding to a11y events. We'd need to instrument the harness to manage this, similar to the way addAccessibleTask functions. We'll also need to add some kind of "checkBeforeFinishing" function to ensure all events and cache pushes relevant to the test have made it to the parent process. We do this in our existing performance tests by awaiting a final EVENT_SHOW or REORDER. The thing we await is test-specific, and I'm not sure we've got an easy way to generalise at this juncture.

We anticipate a relatively flat performance cost across all tests. If we see certain tests have performance that is significantly degraded when a11y is enabled, this is an area we should investigate further as it indicates an area for performance improvement within the engine :)

Eventually, it'd be nice to have this running in CI on some regular cadence.

Depends on: 2077270
Blocks: a11ytestdev
Type: defect → task
See Also: → 2037965

This Speedometer 3 Perf Compare has a11y enabled on the new revision by force enabling it via accessibility.force_disabled:-1

Profile without a11y
https://share.firefox.dev/4sy66JU

Profile with a11y
https://share.firefox.dev/4Bz8TX8

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: