As we have individual meta bugs for accessibility problems on particular platforms, it is good to have a parent meta bug for cross-platform accessibility issues.
(In reply to Yousuf Philips (jay) from comment #0) > As we have individual meta bugs for accessibility problems on particular > platforms, it is good to have a parent meta bug for cross-platform > accessibility issues. Or simply add each OS meta as a blocker when it applies to that build?
I'm collecting and organizing bugs in the following google doc. https://docs.google.com/document/d/1Z2KwmYfdhBed8upi1RCjgX64aAZzFSb4VmjmDVn-Hb8/edit?usp=sharing (In reply to V Stuart Foote from comment #1) > Or simply add each OS meta as a blocker when it applies to that build? Wouldnt want to spam each of those OS meta bugs and those interested in cross-platform a11y bugs can always add themselves to the CC list here. We should also move all the cross-platform a11y to this meta bug and have the OS specific meta bugs to be just for those OSes, so those looking to fixing OS implementation stuff can focus on that meta bug.
(In reply to Yousuf Philips (jay) (retired) from comment #0) > As we have individual meta bugs for accessibility problems on particular > platforms, it is good to have a parent meta bug for cross-platform > accessibility issues. I cannot confirm with Ubuntu 18.04, LirbreOffice Writer 6.06.2 and Orca master 3.29.91pre. Orca announces correctly information when "Orca MOdifier Key + f" is used.