Making Paginated Reports More Accessible
A few tweaks to your paginated reports can make your reports usable for more people. Your design choices help or hinder your report consumers from accomplishing their data analysis goals. You can adopt accessible design habits to make reports usable for people with visual and cognitive disabilities with a few small tweaks to your normal report creation process. Join this session to discuss how to make reports with good color contrast that work better with screen readers. We'll also talk about how descriptive titles and explanatory text can improve accessibility and make reports easier to understand.Encore Making Paginated Reports More Accessible
A few tweaks to your paginated reports can make your reports usable for more people. Your design choices help or hinder your report consumers from accomplishing their data analysis goals. You can adopt accessible design habits to make reports usable for people with visual and cognitive disabilities with a few small tweaks to your normal report creation process. Join this session to discuss how to make reports with good color contrast that work better with screen readers. We'll also talk about how descriptive titles and explanatory text can improve accessibility and make reports easier to understand.Power BI meets UX Design: Accessible Insights
Power BI meets UX Design: Accessible Insights Imagine creating an amazing report—rich in insights and visuals—only to discover your audience can't use it or struggles to grasp its depth. In "Accessible Insights" we'll dive into inclusive UX design principles, revealing the strategic use of icons, text, and visual cues within Power BI. Stepping into the shoes of users with varying abilities, we'll emphasize the crucial role of empathetic design and uncover the hidden, built-in accessible capabilities of Power BI. Join this talk to learn how to create reports that transcend barriers and speak universally to diverse audiences. After all, accessibility is not just a buzzword—it's a necessity. Speaker Info: Elena Drakulevska is a BI Consultant with a Master’s in Telecommunications Engineering from Politecnico di Milano and she’s currently based in Vienna, Austria. With a couple of years of experience across various industries, she brings a unique perspective to the intersection of tech, business, and design. Passionate about both Power BI and UX Design, she finds immense joy in blending the two to create impactful data visualizations. As a fresh speaker at numerous data conferences and the author of her blog Moonstory, she shares her insights and expertise with a global audience. When she’s not working magic with data, Elena can be found exploring the world, picking up new languages, doing yoga, and immersing herself in great books. Zoom details Topic: September 2024 - Higher Education Power BI User Group Meetup Time: Sep 23, 2024 01:00 PM Eastern Time (US and Canada) Join Zoom Meeting https://davidson.zoom.us/j/92198729382?pwd=RvOoXZlYyrWibTI2A2556sTLgcaWNJ.1 Meeting ID: 921 9872 9382 Passcode: 473862
PowerBi report fails accessibility - Id attribute value must be unique per WCAG2.0 411
Is Microsoft planning to address the accessibility issues in PowerBi Service? Id attribute value must be unique per WCAG2.0 wcag411 Ensures every id attribute value is unique more information Link opens in a new window Element Location: iframe symbol[viewBox="0 0 20 20"]:nth-child(79) <symbol viewBox="0 0 20 20" id="checkmark_circle_20_regular" xmlns="http://www.w3.org/2000/svg"> Document has multiple static elements with the same id attribute: checkmark_circle_20_regular Related Node <symbol viewBox="0 0 20 20" id="checkmark_circle_20_regular" xmlns="http://www.w3.org/2000/svg">Accessibility issue in Power BI report server 2023 for grouped elements
Hi All, We have recently upgraded our Power BI reporting server to Version1.16.8420.13742 (January 2023) . We are facing an issue regarding the tab order for report elements in the reporting server. The tab order defined while developing the report in Power BI desktop (jan 2023) works as intended when the elements(slicers,text boxes etc.) are not grouped, In Desktop application, Power BI service and Reporting server. However, when we have grouped elements the tab order doesn't work as intended and is random. In the desktop application and power Bi service it works fine but not in the reporting server. Steps to replicate the scenario: Page 1 with Individual elements present without any grouping, Tab order defined under selection view for individual elements Page 2 with few elements logically grouped, Tab order defined under selection view for individual elements and groups. Uploading the report to Power BI reporting server and using keyboard to navigate Please could you help us on the same, on whether it's a known issue or any solution to resolve the same.
Change Report theme by clicking a button on the Report
Hi there, Can we add a button or some slicer on the Report which will change the Report Theme on the fly\? Button / slicer can have few pre-defined options that can help users to change theme as they prefer and also help users with Color Blindness to still read through the reports, covering the accessbility requirements? Thanks, SSUsing a screen reader with Report Server (on premise)
Dear Community, our Power BI report must also be usable for users with disabilities. So if a user uses a screen reader, it must be able to process the contents of the Power BI report. If we save our Power BI report in the Power BI Service and call it up there, the screen reader can, for example, navigate from cell to cell in the table and read the values aloud. However, if we save the Power BI report on our local report server, the screen reader cannot process the report. We use JAWS as our screen reader. If any of you have had similar experiences and can help us solve this problem? Thank you very much!
