• 1 Post
  • 140 Comments
Joined 2 years ago
cake
Cake day: July 12th, 2023

help-circle
rss
  • The thing is, you need to make proper PDFs with properly structured content with proper metadata for screen readers to be able to access the content in the PDF in a logical and sane way. This is what the OP is tasked to do, and why they are looking for help. So I’m not sure what you mean by “try just using screen readers.”


  • I’m dealing with this right now too.

    My advise is to ditch the PDFs where possible, and go with HTML documents. They are far easier to make accessible. The down side is you can’t easily pass them around in a self contained way that isn’t a bit wonky compared to a PDF or DOCX. But if you just link to them in a course, or otherwise expect students to just access them in a browser, HTML pages can work well.

    PDFs have always been a nightmare, and the new accessibility rules are making thousands of people in education finally realize that.
















  • Well, it seems like splitting a tab into two is just two tabs: read: we can already have two or more tabs in all modern browsers. But “side by side tabs” describes what is actually happening.

    Honestly, this is a difficult one to name. Even though splitting a tab into two isn’t what’s going on, “split tabs” might be the best they can do. It’s just more evidence that this feature is a bit weird, and why it hasn’t been a feature in Firefox, Chrome and Safari yet. Difficult to name succinctly and correctly, and it basically starts doing window management inside of a browser window.

    Also, why stop at splitting the tab in half? Lets stack them too and have a quad view with a tab in each quadrant of the main tab.

    Edit: ohh, call them Subtabs. And put them in a tab next to normal tabs.