So, according to the Syllabus, I'll have to first design the algorithm, which, if I remember correctly, is basically saying, to do this, the script will have to add x and devide by z then do that. Which, I'm reasonably good at, and then they want us to do something painful. That is, having to write down my code on a piece of paper. Which is painful, because I'll have to tell my aide every, single, symbol, and, every, single indentation if Pascal has that. So, It'll be fun to see  what they'll make us do.

I almost forgot, they also want us to comment our code, which, for the love of god I hate doing with a passion. I know its something good to do, like if later on I'll need to do a rewrite, but its just like a waste of energy for me.

Hello,
@1: take my deepest condolences.

1. Regarding accessibility no, as long as you use command line compiler, I don't know about ides.
2. No, powered to 10. I would rather use bath script than Pascal, personal opinion.
3. No. It is taught in schools, that's true, but that's simply about the fact, that many schools, including universities are simply not modern. Pascal is a very old functional language without oop and while its newer forks introduce some object oriented programming, the result is quite weird.
4. None of that. Instead of { and }, in Pascal, you use begin and end.
5. not anymore... luckily.
6. Yes, they definitely should.
7. Definitely not. I don't know about Pure basic, as I never used it, but BGT in terms of audiogames development is a much better choice than Pascal. Videogames development would be another thing though, here you would probably have to decide between Pascal and PB.

As for dictating your code to paper, if you can't actually simply print it, one thing, which you may find useful on Pascal is, that it's case insensitive. Thus you don't need to spell names of things character by character, but can actually say them as normal words.
As for Pascal's popularity, this is of course hard to summary objectively, but from all kinds of statistics I've seen, I don't remember a singleone where pascal would have at least middle place. There are few projects using it currently, Cheatengine for example if I remember right was made in Pascal, but overall the language is dying, if not dead already.
So if I was in your place, I would use it just for the school, and invest the time to something more useful.

Best regards

Rastislav

@5
Even U.S. universities do bad at this.  See also every school that teaches C as a first programming language while expecting good results.  I suspect your schools don't care because updating it is expensive, and whatever language you learn in high school doesn't matter anyway, because high school level programming stops very far short of even introductory university-level courses in most cases.

Commenting in the way I describe isn't painful.  I suspect that the actual problem is that your thought processes are not yet developed enough for it to be painless.  Good comments come from a  very good understanding of what you're writing before you write it, or from the points where it turned out the obvious understanding was wrong.  But that requires some degree of proficiency that you may not have yet.  Also I'm not saying I comment every file--good code that does simple things stands alone.  But from Synthizer's internals, as something I would consider a good comment which I happen to have open in another window:

/*
 * Buffers hold decoded audio data as 16-bit samples resampled to the Synthizer samplerate.  The following entities are involved:
 * 
 * - A BufferData holds the data itself.
 * - A Buffer holds a reference to a BufferData.
 * - A BufferChunk holds a non-owning reference to a chunk from a buffer.
 * 
 * A BufferReader type is also provided, which provides convenience methods for reading without having to deal with assemblying objects yourself.
 * 
 * Design justifications/explanations:
 * 
 * - We use 16-bit samples because this is enough for audio playback, and it cuts ram usage in half w.r.t. floats.
 * - We store data in noncontiguous chunks in order to assist low memory systems, and also because this makes it harder for someone to just copy audio data out with a debugger,
 *   since doing so would require walking our internal structures. Also, branch prediction should make reading cheap.
 * - We resample first for CPU usage purposes.
 * - A Buffer and BufferData are separate types because we can expose Buffers through the C API, which will allow us to offer a BufferCache in future,
 *   rather than making everyone implement this themselves.
 * 
 * Most of this file is inline because otherwise things get expensive very quickly short of compiling with LTO and optimization and it would be nice to be able to use these in debug builds.
 * */

You still have to read the code to fill in the gaps, but the comment fills in the gaps the code doesn't explicitly talk about, and you get an overview of what the literally 100 plus lines in this file are going to be doing without having to read them all first.

Now obviously commenting how school is probably going to want you to, that's going to suck.

@op, I can tell you that I have never seen pascal used in anything I've downloaded other than cheat engine and Innosetup. Pascal is pretty much dead. Its been dead for a long, long time. It doesn't help that there are like 3 different variants of it either (object pascal, pascal, turbo pascal, delphi pascal...). If they want to teach you something unusual, they'd be better off teaching you Ada. As for answers to your questions:
1. Are there any hurdles I'll have to jump through? IE, inaccessible IDE, compillor or some other reason? Or is it accessible out of the box? Or do I have to do anything specific for accessibility with NVDA?
There is a compiler -- free pascal -- that's just CLI-based. There's an IDE too, but that's pretty much entirely inaccessible.
2. Would you recommend it for audiogame development, or just regular software development in general? Or do you suggest I just deal with it to pass my class?
Deal with it to pass your class. You have no reason to use it anywhere else, and no modern workplace even uses it. (That makes me think of COBOL... I don't even think anyone uses that anymore either.)
3. Is it modern? I know it has some age behind it, but python does as well, and its still being developed and widely used.
The difference between Python and Pascal is that Python was made in 1990 and is still actively maintained; Pascal was made in 1970 and, to my knowledge, no one maintains a compiler for it anymore.
4. Does it use indentation or braces? I'll find that one out when I get to the site, but I'd just thought I'd ask here as well.
Neither. I'll show you a hello-world program in a moment.
5. Do you actually use it?
No. I have no use for it anywhere.
6. Do you think Caribbean schools should teach something better? Or is it fine for basic teaching?
By far, yes. They should. They should be teaching you C/C++ like every other university does.
7. Would you take Pascal over PB and BGT? Or are they all equal?
No.
As a hello-world program... from Rosetta Code:

program HelloWorldGraphical;

uses
  glib2, gdk2, gtk2;

var
  window: PGtkWidget;

begin
  gtk_init(@argc, @argv);

  window := gtk_window_new (GTK_WINDOW_TOPLEVEL);

  gtk_window_set_title (GTK_WINDOW (window), 'Goodbye, World');
  g_signal_connect (G_OBJECT (window), 
                    'delete-event',
        G_CALLBACK (@gtk_main_quit),
        NULL);
  gtk_widget_show_all (window);

  gtk_main();
end.

Yes, the period with "end" is required.

what in the world is oop?

@10 OOP is object oriented programming. Also known as how you sound cool when you want to talk about how you use classes for stuff in a job interview.  OOP features just means "has classes and inheritance" basically.

I need to start commenting like you, camlorn. I hardly ever do. I'll probably just have a comment at the top of the file, because seeing
"""
This function does blah, blah blah and blah.
It returns blah.
It takes these arguments, a, b, c, d, e, f, oh and also g.
"""
And then every like third line has
# This does this.
That drives me crazy, personally. But large comments at the top of files like that are actually useful.

Lol school again.

Okay, in case anyone wanted this, I found an opened source Pascal game. But don't ask me about the acessibilty. Its truly a cross platform game, minus Android as usual.

http://www.hedgewars.org/download/relea … .0.tar.bz2

Maybe this can benefit somebody.

You're correct in saying that it died off before VB classic did, but let me lay out the timeline a bit, so you get how old Pascal and BASIC are. I'll explain the creation and increase in popularity throughout the 70's, then I'll skip ahead to the 90's when the languages reached their peak among PC programmers.

• 1964: John G. Kemény and Thomas E. Kurtz create the original BASIC (Beginners, all-purpose, symbolic instruction code) at Dartmouth College, after being frustrated by Fortran.

• 1970: Niklaus Wirth creates Pascal, named after the famous Blaise Pascal, after becoming frustrated with Algol60 and failing to improve it with the AlgolW project.

• 1973: "101 BASIC Computer Games" is published by David Ahl, and BASIC's popularity on minicomputers such as the DEC PDP series and HP 2100 series, increases.

• 1975: Microsoft's first product was, in fact, a version of BASIC for the MITS Altair 8800, one of the first personal computers.

• 1976: Microsoft ports BASIC to the MOS Technology 6502 microprocessor.

• 1977: UCSD Pascal, one of the early versions of Pascal to be ported to various personal computers, is created at the University of California, San Diego.

• 1978: Steve Wozniak creates Integer BASIC for the Apple I, which is added to the ROM chip for the Apple II.

• 1979: Apple Computer publishes Apple Pascal, based on UCSD Pascal, for the Apple II.

• 1989-1990: Turbo Pascal 5.5 and 6.0 were released. These were the first to bring object-oriented features to IBM PC users, since Object Pascal was created by Apple and had been used by Macintosh programmers since 1985.

• 1991-1992: Microsoft introduces Visual Basic 1.0 for Windows 3.1 and DOS.

• 1993: Visual BASIC 3.0 is released. This was the first extremely popular version of VB, and was the first to support reading and writing of Access databases. Borland releases Turbo Pascal 7.0, the first version to support creation of Windows executables and DLL's and introduce syntax highlighting.

• 1995: Microsoft introduces Visual BASIC 4.0, the first version that could create 32-bit as well as 16-bit Windows programs. Borland introduces Delphi 1.0 for Windows 3.1, based on Turbo Pascal for Windows, and is one of the first examples of Rapid Application Development.

• 1996-1997: Borland releases Delphi 2 and 3. Delphi 2 introduced support for 32-bit Windows, and Delphi 3 introduced support for the COM architecture.
  Microsoft introduces Visual BASIC 5.0, the first version to exclusively support 32-bit Windows and support for user-created controls.

• 1998: Visual BASIC 6, the most popular edition of VB classic, is released. A major improvement was introduced in VB6, that is, to allow creation of web-based applications. Borland, then called Inprise, releases Delphi 4.0, which includes improvements such as method overloading, dynamic arrays, Windows 98 support, Java interoperability, and high performance database drivers. It was the last version shipped with Delphi 1 for 16 bit programming.

Whereas Visual BASIC was replaced with VB.net, Delphi still exists. Inprise, which went back to the Borland name, now known as Embarcadero, still sells Delphi. Although Borland/Embarcadero did produce versions of Delphi for the .net Framework, support for delphi.net was dropped in 2009. The latest version of Delphi is Embarcadero Delphi 10.3, codenamed Rio.

Hmm, so i can do it in a text editor? Because lazarous is inaccessible as lemons.

I would suggest you use the Free Pascal compiler, which has support for the Turbo Pascal syntax. There is a VS Code Extension for Pascal if you want to use it.