We want LI to be one of the friendliest places on the internet, where lawyers and law students help each other with their career related queries and occasionally discuss other stuff that might affect their lives too. In other words:
1. Be kind, respectful and helpful to each other.
2. Be bona fide, truthful, genuine and curious.
3. Assume the best intention of others.
Therefore, in using the site, you must agree to do your best to uphold these community guidelines.
Note that what you find here is written and moderated by anonymous people on the internet.
Therefore everything you read here is very likely unverified, rumour, speculation and/or downright false.
In continuing to read anything here, you must therefore agree not to take anything you read here as factual and that you will exercise due caution, diligence and common sense before acting on any information you may come across here.
You also agree to report any inaccurate or malicious comments with the buttons. Moderators take action within 24 hours, as required and appropriate under law.
Our full terms and conditions apply too.
Do you solemnly agree to all of the above?
As for (seeming to be, at least to you) nice, the vast majority of people I look up to (and therefore try and emulate), both in and outside the legal profession, are people who I know well and who are very kind, generous and thoughtful themselves; I doubt you would find me very remarkable in comparison to them. Also, as far as this thread is concerned, there hasn't been any impoliteness or any other form of foolishness I have had to deal with (so far at least), so maintaining my equanimity hasn't been all that hard. For example, on another thread started by a visually impaired student, somebody made a very patronising suggestion as to why a certain career option would be easier for the blind or visually impaired and used very condescending language in talking about that, conduct which (for me at least) falls under the heading of "foolishness"; even a cursery glance through this thread (at least at the time of writing) should demonstrate that foolishness is conspicuous here by its absence. For those who have observed the painful and vulgar ad hominem and below-the-belt jibes that happens on some other threads this may be surprising, but this is more to the credit of fellow LI comment writers than to me, because, rather than yielding to the temptation to troll, they asked good questions, the sort of questions reasonable people who want to do the right thing would ask, and which deserve an answer.
As for screen reader recommendations, I use Non-Visual Desktop Access (NVDA). This is free to download (you get an optional donate dialogue box, which you can skip without impairing any software functionalities, as far as I know at least) and the only screen reader I have used properly. The most common choices of screen reader for blind people (on windows at least) are NVDA and Job Access With Speech (JAWS) (this latter requires payment, but I believe there is a free trial version). If you wanted to carry out an accessibility test of LI, you could try downloading NVDA and/or JAWS and reproducing this.
We didn't realise that there was a difference in the the comments section when signed in vs as a guest from the homepage (I presume?). Will see whether we can reproduce this!
Is there a specific screenreader software you would recommend to use on Windows, Mac or Linux for reproducing the website usability issues, or are they all fairly similar in capability and any of them would work?
That said, the mods have generally done a great job on this thread, you missed nothing interesting, and thank you to all readers for asking interesting questions and to OP for the amazingly patient and insightful responses.
Thank you also for your feedback on the screenreader UX issues. We'll see if we can reproduce and fix this.
Maybe its not awkward but it seems it would be time consuming for sure.
With editing as well, yes it does help to hear your work read aloud some times, but more often than not I need to see the different paragraphs and how theyre structured when I edit. I move around sentences a lot and it would be annoying to me if I couldnt see and had to rely on screen reader to know whats going on. Perhaps im not taking into account how well people can adapt.
In any case Im glad you find these tasks to be doable and not too cumbersome. Good Luck to you! and thanks for answering stupid questions!
Second, I am sorry we didn't get to read your (non-abusive, of course) pun! Laughter is always a nice way to smash barriers, of whatever type. Call me ghoulish if you like, but I actually kind of want to read some of those comments marked "trollish" and placed into the "unpublished" pipeline by mods (out of a morbid sense of curiosity just to see how badly those people would have embarrassed themselves if they had been published) :)). Also, I am glad that you seem to have learned/taken away something useful from this yourself.
2. I do all my academic work by typing on a laptop, just like how the vast majority of students these days would, with the only difference being that I have a piece of software (called a 'screen reader') that reads out everything I type and everything else on the screen to me as well.
Also how do you write your papers like do you write in any different script or do you use laptop for that?
2. Heinonline, JStor and Manu are accessible. SCC Online is bad, but is gradually improving. I am not sure if LI reported on this at the time, but Indiaβs first blind Rhodes Scholar got into quite a verbal spat with them on Twitter a number of years ago because they effectively said that demands by the blind to make the database were unreasonable, we should be thankful for what we have and go home. As he pointed out in an interview with Jurist, the incremental improvements that have been made to SCC Online have been the result, not of reformed attitudes on accessibility on part of those who run the database, but because of other website improvements they have been making (I wonβt jump any further on this hobby horse).
3. I have found this to be the case as well for research projects. I, too, write and rewrite. In fact, in a way, I find it easier! A piece of advice I often hear is that, to understand the flaws in oneβs writing, one should try reading it aloud. My screen reader is reading it back to me, so I am constantly listening to what I am writing, in real time! As for footnotes, my screen reader indicates that I have inserted a footnote and where it is, and I can put in whatever information I need to in there. At the end of every page, I can read and navigate through the footnotes, just as a sighted person would do. Obviously, itβs more time consuming, but hardly βawkwardβ. I have to keep in mind all the stylistic conventions surrounding fonts and so on and apply them (using keyboard shortcuts in Word) as best I can. There are functionalities in my screen reader that can be turned on and off to report things like font colour, attributes, size and so on, and other features like alignment, which I turn on to check my application of formatting requirements. While obviously it is reading the text and announcing these formatting features at the same time, I canβt just go over something once, but have to do so multiple times. But how different is that from what you as a sighted person would do? Wouldnβt you proofread your projects multiple times prior to submission?
1. If you work at an institution with reasonably good accessibility infrastructure and a good disability service (I know this sounds largely like an institution in the west at this point, but let's go with it for the sake of argument, as such things should slowly be coming to India, and this point would translate well if you were to work as an academic in the west), follow all reasonable/sensible advice you receive from those in your institutional administration to make your teaching materials accessible. For example, if they tell you that the best accessibility practice would be to upload/assign a PDF as a reading on a Virtual Learning Environment after putting it through SensusAccess or some equivalent accessibility conversion package first that converts image-based PDFs into accessible typed text, it might be better to just do it, rather than see it as βanother useless request from the administrationβ. Remember if you donβt, your student will have to, only increasing the unfair burden on them. At the same time, use your discretion wisely and follow your instincts. Ask yourself, "Is this advice necessarily the best way to do things for a blind person?". This might especially arise if, for example, a document with lots of Mathematical symbols is involved. Therefore, in one sentence, listen to your student, good advice on accessibility practices and your instincts.
2. I think any student with support needs would appreciate if you asked them what they needed in a classroom to better facilitate their learning. Even if you know, just ask, because the answer might be different from blind student to blind student, as not all blind students are the same (one may have a tiny amount of vision where another has none, one might have learned Braille where another hasnβt, one may choose to ask a fellow student to support them by being a notetaker while another might be able to juggle hearing the professor speak while at the same time typing out their notes and listening to the screen readerβ¦ you get the point, we arenβt a monolith). But never, ever, ask about or discuss things like accessibility or exam/assessment adjustments in front of other students. You are opening your future blind/disabled student up to potential humiliation and bullying, which you donβt want. In addition, if you are going to do some kind of exercise that may not be the typical back-and-forth of students discussing and answering the teacherβs questions, e.g., getting a student to read something aloud, ask again in advance how your blind student can/will do it. To go with the reading aloud example, some blind people may not find it easy to read aloud, either because they havenβt learned Braille/donβt use it often or find it hard to coordinate between listening to a screen reader, while at the same time reading, which might make them feel embarrassed or humiliated in participating in such an exercise.
3. Learn to be as verbal as you possibly can. Remember, everything you do visually (writing on a board, illustrating how price elasticity of demand works etc.) has to now be described. Get very good at describing in a way which isnβt spoon-feeding. One very embarrassing thing that often happens in classes with blind students is that, when there is a show of hands to answer a question, the teacher says βyesβ while looking at/pointing to the blind student. This will leave a blind student confused as to whether you want them to answer or not, leading to awkward pauses. Always say the name, or if you really have trouble remembering names, donβt break these awkward pauses with impatience; remember your student is navigating layers of judgementalism from their fellow sighted course-mates, in a classroom designed for and by sighted people, in conformance with the expectations of a sighted society, in a sighted world.
4. Returning to point 1, it is always good practice to let your student, university library and university disability service (if and where any such thing is available) know of what textbook(s) will be assigned in class in advance. If chapters from multiple books will be assigned, this is also fine, just let all applicable stakeholders know. This gives time for accessible copies of the set text(s) to be procured well in time from publishers if and where available, or scanned by librarians/disability support officers where that is needed.
5. If you are teaching a class on legal research/database usage, learn how databases are perceived by screen reader users. In simpler terms, understand how to navigate legal databases using only keyboard keys/shortcuts, rather than a mouse. Instructions such as βscroll hereβ or βclick on the red arrowβ wonβt work, with workable alternatives being things like βScroll using tab/arrow keys [where appropriate]β or βselect the βadvanced searchβ optionβ, because screen readers canβt be used with a mouse meaningfully, and they read out the names of icons/buttons to their users, and do not describe colours/arrows. If you are training your student to use one of the prominent western legal databases (Westlaw, Lexis Nexis etc.), find out if your university/law school can arrange for your blind student to receive training from specialists who work for those databases who know how to train blind people to use them; if your law school hasnβt done such a thing before, get them to do it. Relating to verbalising and descriptions above, remember that stuff their sighted counterparts will take in by looking will often have to be told to a blind person. For example, the convention of underlining case names in the OSCOLA citation style is something the sighted will pick up organically from looking at articles/booksβ footnotes/end notes, but something you may have to tell a blind student. Donβt be afraid to mention this as assignment feedback, if necessary. Suppose you are marking a Tort essay that is to be written using OSCOLA and you see that a blind student isnβt underlining case names, something they should have learned about in legal research classes, just give it as feedback, they may not have been told by a careless sighted colleague of yours and may not be told again by colleagues who may take pity or whatever, but instead have such things come back to bite them later.
How do you write research projects ? For me a lot of that writing is rewriting and editing ? Wouldnβt that be awkward and difficult with speech to text ? And footnotes and citations ? How do you manage that while being blind ?
NB: If in any of the other replies I have given above, if you have received a reply from "Guest", that is likely because I forgot to change the display name from "Guest" to "Blindlaw2003".
2. Following from no. 1, better training should be given to academics on how to communicate accessibly (e.g., describing slopes of demand/supply curves in an Economics class).
3. Networking problems: I often find it hard to network on my own in various situations, because the nondisabled feel uncomfortable to come talk to me for various reasons. Law schools can easily solve this problem by introducing a system such as having a blind person be accompanied by a sighted guide in a networking situation who can help them navigate around the room, while at the same time, helping them find and talk to people. There are precedents for this being done, read a book called βHaben: The Deafblind Woman who Conquered Harvard Lawβ, by Haben Girma (the first hearing-impaired and visually impaired person to attend and graduate from Harvard Law School with a J.D.). She describes how the Office of Career Services sent a careers advisor with her into an employer networking event to help out precisely with this.
LI has one question - is the convos section of LI accessible and well useable on screen readers or other assistive software? Any quick fixes or big problems you have encountered in navigating that we could improve or look into? Very grateful for any of ideas or tips!